System and method for generating automatic user interface for arbitrarily complex or large databases

ABSTRACT

A software system automatically and dynamically generates a fully functional user interface (UI) based upon, and connected directly to, an underlying data model (as instantiated within a relational database management system (RDBMS)). The UI derives from an automated interrogation of the RDBMS, and comprises all mode displays (e.g., browse, search, edit, add) for all tables, and a full complement of mechanisms—integrated directly into the mode displays—for representing, navigating, and managing relationships across tables, regardless of the complexity of the underlying RDBMS schema. It utilizes a hierarchical “context stack” for suspending the working state of a particular table while “drilling down” to work with related-table information and return relevant changes to the base table. The embodiment further provides methods to enhance and extend the internal representation of table structures, constraints, relationships, and—special requirements (“business rules”) for improved revelation of the schema structure through external interrogation.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 12/930,849, filed Jan. 19, 2011, which is a divisional of U.S. patent application Ser. No. 11/925,236, filed Oct. 26, 2007, now U.S. Pat. No. 7,885,981, which is a continuation of U.S. patent application Ser. No. 10/428,209, filed Apr. 30, 2003, now U.S. Pat. No. 7,318,066, which is a continuation of International Application No. PCT/US01/42867, filed Oct. 31, 2001, which claims priority to U.S. patent application Ser. No. 09/703,267, filed Oct. 31, 2000, now abandoned, and U.S. Provisional Patent Application Ser. No. 60/276,385, filed Mar. 16, 2001.

COMPUTER PROGRAM LISTING

The computer program listing submitted on compact disc is hereby incorporated by reference. The compact disc contains the following directory structure:

File Name and Path Date of Creation Size in Bytes Schemalive/AddEditForm.jsp 10/30/2001 36,431 Schemalive/BalloonHelp.jsp 10/30/2001 2,375 Schemalive/Browse.jsp 10/30/2001 42,376 Schemalive/DataDictionary.jsp 10/30/2001 1,501 Schemalive/DoAddEdit.jsp 10/30/2001 18,925 Schemalive/DoViewGenerator.jsp 10/30/2001 1,356 Schemalive/Error500.jsp 10/30/2001 3,670 Schemalive/ExpiredSession.jsp 10/30/2001 3,853 Schemalive/OutOfSequence.jsp 10/30/2001 4,306 Schemalive/showSession.jsp 10/30/2001 5,317 Schemalive/common/EmptyParamCheck.jsp 10/30/2001 592 Schemalive/common/EntryPoints.jsp 10/30/2001 319 Schemalive/common/GlobalHeaderHTML.jsp 10/30/2001 4,096 Schemalive/common/GlobalHeaderJavascript.jsp 10/30/2001 13,557 Schemalive/common/GlobalHeaderVARS.jsp 10/30/2001 952 Schemalive/WEB-INF/web.xml 10/30/2001 3,783 Schemalive/WEB-INF/classes/Connection.properties 10/29/2001 186 Schemalive/WEB-INF/classes/common/Debug.java 10/30/2001 1,591 Schemalive/WEB-INF/classes/dbUtils/CustomCaps.java 10/30/2001 552 Schemalive/WEB-INF/classes/dbUtils/CustomDrillDown.java 10/30/2001 1,218 Schemalive/WEB-INF/classes/dbUtils/CustomDropDown.java 10/30/2001 1,094 Schemalive/WEB-INF/classes/dbUtils/CustomDropDownComponent.java 10/30/2001 968 Schemalive/WEB-INF/classes/dbUtils/DataDictionary.java 10/30/2001 8,892 Schemalive/WEB-INF/classes/dbUtils/DataDictionaryServlet.java 10/30/2001 6,864 Schemalive/WEB-INF/classes/dbUtils/DataDictionaryTD.java 10/30/2001 11,537 Schemalive/WEB-INF/classes/dbUtils/MasterDetail.java 10/30/2001 2,537 Schemalive/WEB-INF/classes/dbUtils/MasterDetailServlet.java 10/30/2001 3,922 Schemalive/WEB-INF/classes/dbUtils/SQLUtil.java 10/30/2001 3,390 Schemalive/WEB-INF/classes/dbUtils/TableDescriptor.java 10/30/2001 21,728 Schemalive/WEB-INF/classes/dbUtils/ViewGenerator.java 10/30/2001 21,979 Schemalive/WEB-INF/classes/HTMLUtils/Balloon.java 10/30/2001 1,325 Schemalive/WEB-INF/classes/HTMLUtils/BalloonHelp.java 10/30/2001 5,264 Schemalive/WEB-INF/classes/HTMLUtils/TableDescriptorDisplay.java 10/30/2001 41,339 Schemalive/WEB-INF/classes/sessionUtils/ManageSession.java 10/30/2001 1,319 Schemalive/WEB-INF/classes/sessionUtils/StackElement.java 10/30/2001 5,045 Schemalive/WEB-INF/classes/sessionUtils/StackTag.java 10/30/2001 8,732 Schemalive/WEB-INF/classes/sessionUtils/StackTagExtraInfo.java 10/30/2001 581 Schemalive/WEB-INF/classes/tagUtils/ViewTag.java 10/30/2001 2,461 Schemalive/WEB-INF/classes/tagUtils/ViewTagExtraInfo.java 10/30/2001 785 Schemalive/WEB-INF/taglib/stack.tld 10/30/2001 1,219 Schemalive/WEB-INF/taglib/view.tld 10/30/2001 922 SQL/CreateSchema.sql 10/30/2001 32,698

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to the field of data processing, and more particularly to relational computer databases, and to systems and methods for automatically generating without any custom programming a user interface for the database, and/or a complete application utilizing the database.

2. Description of the Related Art

Modern databases—and in particular, complex or large databases which serve many concurrent users—are constructed as “client/server” or “n-tier” (client/server/server) systems, wherein specialized components perform separate (and carefully delineated) functions. At a minimum, such systems are generally composed of a “back-end” relational database management system (RDBMS)—which maintains and manipulates information according to requests submitted by other components or software processes (or expert human administrators) via open-standard query languages (i.e., SQL)—and a “front-end” presentation layer or user interface, which mediates the end-users' work with the back-end data.

Developing such a database system consists both in defining the organizational structure to be used by the back-end for storing data (that is, the complement of tables which store data, and the relational links between these tables)—known as a “schema” or “data model”—and in building a front-end program (or “application”) via which end-users can manipulate this data (and which communicates with the back-end on the users' behalf). And although the back- and front-end components must be closely synchronized and reflect similar structures, these respective development efforts are typically rather separate—with the requisite synchronization and parallels in structuring being effected only manually.

Moreover, the construction of front-end applications is generally undertaken using conventional third- or fourth-generation computer languages, which require by-hand coding at a very low level of functionality. Current tools for easing the development burden are limited to fairly specific (and, still, fairly low-level) uses—among them, providing more sophisticated or “richer” controls for manipulating individual data elements; associating individual user-interface elements with specific back-end storage locations; or—at best—offering “form generator” or “wizard” facilities to automatically generate the code for a simple VI display which manipulates a single underlying (back-end) data table.

Even with such tools, considerable work remains in building a complete, fully functional VI for a back-end schema of any appreciable size or complexity—especially where industrial-grade performance and reliability is required. And as enterprise-scale data models continue to grow, the attendant explosion of manual-coding requirements quickly becomes unwieldy—and eventually, untenable.

BRIEF SUMMARY OF THE INVENTION

It is an object of the invention to provide a complete and fully functional user interface (UI) for any arbitrarily complex or large database schema, without any custom software programming.

It is another object of the invention that, once a back-end schema has been designed and constructed within the RDBMS, the system can automatically “interrogate” this schema, and “absorb” its structure into an internal cache (or, at the cost of real-time performance, the internal caching mechanism can be sidestepped).

It is a further object of the invention to present to end-users, for any arbitrarily complex or large database, a comprehensive application through which the back-end can be operated, and through which all conventional database activities—searching, listing, adding, editing—can be supported, across all base-tables comprising the schema.

It is yet a further object of the invention that the application so presented reveals (and enforces) the relational/hierarchical organization among the tables within the back-end via smoothly integrated UI mechanisms which are embedded directly into the base-table screen displays—providing a natural, powerful, and easy-to-use environment for managing complex data relationships and interactions.

One embodiment (the “reference implementation”) of the present invention achieves these and other objects by providing a system, currently written in Java and JSP, which automatically and dynamically (“on-the-fly”) generates (in HTML, Javascript, and HTP/CGI code), a fully functional UI system, based upon, and connected directly to, the underlying data model (as instantiated within an Oracle8i SQL RDBMS). The UI is built based on an automated interrogation of the RDBMS, either as needed (on-the-fly) or by building an in-memory representation of the data model. The generated UI comprises all mode displays (e.g., browse, search, edit, and add) for all tables, and a full complement of mechanisms, integrated into the mode displays for representing, navigating, and managing relationships across tables. This embodiment has the capability of creating such a UI where the underlying RDBMS is complex and comprises a plurality of tables, constraints, and relationships. It utilizes a hierarchical “context stack” for maintaining (and suspending) the working state of a particular table (comprising selected record, display “mode”, pending form-field entries, in-effect search-filter parameters, Browse-mode scroll position, and any filter constraints imposed from above stack contexts) while “drilling down” across relationships to work with related information (in a possibly constrained working context) and returning relevant changes to the parent-context table, and a corresponding UI convention for displaying and navigating this stack. The embodiment provides a set of rules for traversing/navigating the context stack. It further provides naming conventions and annotational methods for enhancing and extending the representation of table structures, constraints, and relationships within the back-end so as to more fully support revelation of the schema structure through external interrogation.

BRIEF DESCRIPTION OF THE DRAWINGS

The following briefly describes the accompanying drawings:

FIG. 1 is a normal “browse mode” display from the reference implementation.

FIG. 2 is a normal “search mode” display from the reference implementation.

FIG. 3 is a normal “edit mode” display from the reference implementation.

FIG. 4 is a normal “add mode” display from the reference implementation.

FIGS. 5A-5W is a diagram of the demonstration RDBMS schema from the reference implementation.

FIG. 6 is a diagram of the relationship types comprised in the paradigm of the present invention.

FIG. 7 is an annotated screen dump showing the active elements in a “browse mode” display.

FIG. 8 is an annotated screen dump showing the active elements in an “edit” “add” or “search” mode display.

FIGS. 9A-9E show an exemplary “master/detail drill-down” and a doubly-constrained subordinate table search as rendered in the reference implementation.

In addition, the complete source code for the reference implementation, and scripts for creating the reference demonstration schema (and demonstrating the extended back-end annotational methods employed) are set forth at the end of this description.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The preferred embodiment of the invention, as illustrated in FIGS. 1 through 9E, corresponds in most respects to an implementation of the invention being developed under the trademark SCHEMALIVE™ which is herein referred to as the “reference implementation.” The preferred embodiment is further represented substantially in full by the reference-implementation source code files, documentation and scripts in the appendices accompanying and incorporated by reference into this application, as further described in the text that follows. The preferred embodiment includes in addition some further developments which are herein described which have not as yet been rendered in the reference implementation.

Although the invention has been most specifically illustrated with a particular preferred embodiment, it should be understood that the invention concerns the principles by which such embodiment may be designed, and is by no means limited to the configuration shown.

As can be more fully appreciated by studying the accompanying source code, the preferred embodiment operates in accordance with a comprehensive and formalized paradigm for presenting a(n end-) user interface to any arbitrarily large or complex relational database schema (or “data model”), as represented via generally accepted data-modeling conventions (comprising the explicit declaration of any cross-table “referential integrity” [RI] constraints, and full exploitation of available native-RDBMS datatype- and constraint-attribute declaration mechanisms) and instantiated within a commercial-grade SQL RDBMS engine (Oracle8i, for example, in the reference implementation). The paradigm encompasses:

-   -   A set of “modes” for interacting with a(ny) given database table         (which modes, taken together, cover all desired end-user         operations which may be effected upon such tables), and a         corresponding display format (“screen” or “window” architecture)         for each mode. These modes comprise:         -   BROWSE (full or filtered, possibly context-constrained) (see             FIG. 1)         -   SEARCH (new or revised, full or context-constrained) (see             FIG. 2)         -   EDIT (full or context-constrained) (see FIG. 3)         -   ADD (full or context-constrained) (see FIG. 4)     -   Certain key screen elements for navigation control/support are         shared across all of these displays (see FIGS. 7-8):         -   A TITLE BAR 712, 814 which indicates current mode, current             table, context-constraint (if any), and filter indicator (if             search-filter is in effect)         -   A TABLE-NAVIGATION HEADER 702, 802 which provides direct             “random access” to any system table, in either Browse or             Search mode, via either a full (dropdown-) list of all             (available) system tables or a short list of (clickable)             “quick links” to key tables. Use of this header will also             reset (and abandon) any nested stack-contexts in effect         -   A CONTEXT-STACK DISPLAY 704, 804 which indicates the active             table and mode at each level in the context stack (described             below), and also allows direct navigation (“pop-up”) to any             suspended (“higher”) stack-level (with abandonment of all             lower levels)         -   A MODE-NAVIGATION BAR 710, 812 which allows the user to move             amongst the various available mode displays for the current             working table (or “stack level”). The list of available             modes varies, dynamically, according to both the user's             access rights (described below) and the current state of the             working session (i.e., whether a search-filter is currently             in effect). The full list of possible mode-navigation             options is: FULL BROWSE, FILTERED BROWSE, NEW SEARCH,             REVISED SEARCH, and ADD. Note that FILTERED BROWSE and             REVISED SEARCH appear only when a search-filter is currently             in effect; if so, the former restores a Browse-mode display             with the most recent filter and scroll-position, while the             latter pre-populates a Search-mode display with the current             filter parameters         -   Additional MODE-NAVIGATION 706 to allow “edit mode” for a             single table record         -   SCROLL NAVIGATION 708 allowing a(n end) user to navigate             through all the records in a table and also allowing the             user to dynamically change the number of records contained             in the webpage displayed (i.e., dynamic page-sizing)         -   HOT LINK 806 for “drill-down” to cross-reference table             (e.g., in the embodiment shown in FIG. 8, “Country”)         -   HOT LINK 808 for “drill-down” to master-detail table (e.g.,             in the embodiment shown in FIG. 8, “City”)         -   CROSS-REFERENCE FIELD 810 to generate dropdown lists of             available foreign-key values (with automatic correlation to             display-name labels)         -   FIELD 811 for free-form text entry, to provide automatic             client-side data validation according to back-end datatype             (for edit/add mode only)         -   SUBMIT BUTTON 816 commits changes, and executes appropriate             mode-switch (and stack-context return, if appropriate)     -   Note that, although not shown in the reference implementation,         DELETE capability is also readily incorporated—as either (or         both) true record-removal from the underlying table, and/or         record “flagging” for UI suppression (with continued         underlying-table record retention)—simply by adding (according         to the user's access rights, potentially) another pushbutton         within the Edit-mode display     -   A set of rules and methods for moving among the modes (and,         hence, displays) for a given table (see “mode navigation” in         FIG. 7), comprising:         -   Explicit (manual) mode-selection via the mode-navigation bar         -   Browse-to-Edit mode-transition for a specific record, by             clicking on a Browse-row's leftmost-column “row label” link         -   Implicit return-to-Browse transitions from other modes:             -   From Edit mode, upon record commit (UPDATE pushbutton)             -   From Add-mode, upon record commit (ADD pushbutton), with                 optional override via an on-screen checkbox setting                 which “locks” user into Add mode for the current table                 until checkbox is cleared, or until user explicitly                 navigates away             -   From Search mode, upon filter commit (SEARCH                 pushbutton), with optional override via an on-screen                 checkbox setting which enables direct Search-to-Edit                 transitions for single-row result-sets, provided user                 has requisite edit rights. In the reference                 implementation, this checkbox setting is                 session-persistent (that is, it remains in effect until                 the user's session terminates, so long as the user does                 not explicitly turn it off); it could as easily be made                 “sticky” to a variety of degrees—lasting for only a                 single search, for a single stack-context session, or                 even across system sessions (via database-stored user                 “preferences”)     -   A set of “relationship types” between individual database tables         (which types, taken together, cover all desired connections         between any two tables), and a corresponding UI convention for         representing each type of relationship “in-place” within the         (single-table) mode displays. As shown in FIG. 6, these         “relationship types” comprise:         -   CROSS-REFERENCE 602 (a.k.a. “foreign key” or “FK”)—single             primary-table record keeps pointer to any single             foreign-table record         -   MASTER/DETAIL 604 (a.k.a. “parent/child” or             “one-to-many”)—multiple foreign-table records keep pointers             to single primary-table record     -   A set of rules and methods both for extending the representation         of any single table (according to its relationships to other         tables) (FIGS. 7 and 8), and for managing (and navigating         across) these relationships (comprising the resolution, display,         and manipulation of cross-referenced elements within a primary         table's display context, and the creation or revision of         related-table information within the context of a primary table         by “drilling down” to a secondary table, constraining the         “working context” of that secondary table as necessary, and         “passing back” relevant changes to the primary-table context)         (see FIG. 9). Said rules and methods comprise:         -   Foreign-key fields occurring within a table—that is, fields             which contain “keys” that uniquely identify cross-referenced             records from secondary (a.k.a. “foreign”, or “referenced”)             tables—are automatically “resolved” for display purposes, so             as to substitute a corresponding (and, presumably, more             meaningful) “name” field from the foreign-table record (in             lieu of the key value itself which, per generally accepted             data-modeling conventions, is generally intentionally devoid             of intrinsic meaning):             -   The paradigm specifies a “default” behavior for                 determining this name field within the foreign-table                 record, based (optionally) upon a combination of                 field-naming conventions, field datatype (i.e.,                 character data), field constraints (i.e., unique                 values), and/or order of appearance within the table                 definition (i.e., first non-primary-key field meeting                 other requirements)             -   In the reference implementation, this field is the first                 one whose name ends with “_NAME”—or, in special-case                 handling for tables containing “LAST_NAME”,                 “FIRST_NAME”, and “MIDDLE_NAME” columns, a composite                 “Last, First Middle” value. Additional special-case                 processing supports successive cross-referencing through                 multiple tables until a “_NAME” field is discovered, if                 (and only if) intervening tables include unique-value                 constrained FK columns. If no name field can be                 resolved, the UI displays the actual key values (that                 is, the primary-key values from the foreign table)                 themselves             -   Alternatively, the rules for determining the name field                 can themselves be made “soft”—that is, specified once                 (globally) by a system administrator, and used                 thereafter to drive all (default) name-field                 constructions. (See the discussion of naming conventions                 and annotational methods, below.)             -   The default behavior for name-field resolution can also                 be overridden with (either or both) “global” and/or                 “local” custom-name definitions for specific tables, as                 described below (within the discussion of extensions to,                 and customization of, the baseline UI paradigm)             -   Auto-resolution of display-names applies to both                 Browse-mode cells (where a single display-name is                 derived and substituted for a given foreign-key value),                 and Add/Edit/Search form-fields (where a dropdown list                 includes the display-names for all foreign-table                 records, and UI actions on this list are correlated to                 the underlying keys)         -   For “master” tables in any master/detail relationships (as             specified via the core complement of naming conventions and             annotational methods, discussed below), record displays             incorporate a “pseudo-field” for each associated             detail-table, which indicates the number (i.e., count) of             corresponding detail (or “child”) records belonging to the             displayed master (or “parent”) record:             -   In the reference implementation, the master/detail                 pseudo-fields are included only for Edit-mode displays                 (so as to allow for streamlined system logic and,                 therefore, improved run-time performance)             -   Alternatively, these pseudo-fields can also be (and have                 been, in alternate implementations) readily incorporated                 into the Browse-, Search-, and Add-mode displays, at the                 cost of added complexity in supporting views (i.e.,                 correlated-subqueries for Browse-mode displays) and                 state-management logic (i.e., transitioning to Edit mode                 for not-yet-completed Add-mode transactions before                 allowing navigation to associated detail-table contexts                 where the user might add dependent “child” records), and                 the attendant performance implications         -   To enhance the run-time performance of Browse-mode displays,             the system automatically generates a corresponding back-end             “view” for every table, which:             -   Resolves all FK displays, per above             -   Incorporates any and all default-behavior overrides             -   By rendering (and, subsequently, executing) this view in                 the native language of the underlying RDBMS (i.e., SQL),                 effectively “projects” this extended representation of                 the table (according to its relationships to other                 tables) from the software (where it is derived) back                 into the RDBMS environment itself, for significantly                 improved rendering performance and reduced network- and                 application-server loading     -   See the discussion, below, of rules and methods for         traversing/navigating the context stack, for more information on         the creation and revision of related-table information within         the context of a primary table     -   A set of user-interface conventions for signaling other         (non-referential) data constraints, and for enforcing adherence         to same, across all Add/Edit/Search forms, comprising:         -   For “required” fields (i.e., underlying table-columns with             “NOT NULL” CHECK constraints, in the reference             implementation), the corresponding data-field labels             (descriptive names appearing to the left of the entry areas)             are displayed in boldface (see FIG. 3)         -   The physical width of text-entry (vs. dropdown) fields—as             well as the maximum permitted length for entered text—is             driven directly by the specified data-length of the             underlying table columns.         -   For text fields whose length-limit exceeds a certain             threshold (globally defined, in the reference             implementation, though potentially user-preference             configurable), the on-screen field is presented as a             multiline, vertically scrollable control with multiple-row             visibility, rather than the default single-row (and             non-scrollable) entry field. (In the reference             implementation, this is an HTML “TEXTAREA” rather than an             “INPUT” field.) Note that this functionality is also applied             to Browse-mode table cells, so that occasional lengthy             cell-entries are made scrollable (and therefore don't             distort an otherwise reasonable table-layout)         -   Required fields (per above)—along with numeric, date, and             text fields (whose length might exceed the threshold             specification described above)—also generate automatic             validation logic which prompts the user to correct any             erroneous or problematic data-entries locally—that is, on             the end-user's (or “client”) computer, before any             communication with the database takes place. In the             reference implementation (which is web-based), this             manifests as client-side Javascript routines—along with all             requisite invocation logic, automatically embedded into the             appropriate entry-field specifications—which are delivered             along with the (system-generated) web-page. Failed             validation (upon field-exit and/or at page-submission time,             depending on the type of validation) puts the “focus” back             into the corresponding problem-field (or the first of             several), highlights (“selects”) the entire field contents,             and displays an informational pop-up dialog box explaining             the problem. This effectively “projects”             constraint-awareness from the back-end RDBMS (where the             constraints are defined) into the front-end client, for             significantly improved performance and reduced network- and             database-loading     -   A hierarchical “context stack” for maintaining (and suspending)         the working state of a particular table (comprising selected         record, display mode, pending form-field entries, in-effect         search-filter parameters, Browse-mode scroll position, and any         filter constraints imposed from above stack contexts) while         “drilling down” across relationships to work with related         information (in a possibly constrained working context) and         returning relevant changes to the parent-context table, and a         corresponding UI convention for displaying and navigating this         stack     -   A set of rules and methods for traversing/navigating the context         stack, among them:         -   The user is always working at the “bottom” (or rightmost,             within the stack display) level of the context stack.             Typically (i.e., at initial system entry, or following             direct access via the table-navigation header), there is             only one level in the stack (that is, no nested or suspended             stack contexts are in effect)         -   Changing modes for a given table (or “stack context”) is             referred to as “lateral” or “horizontal” movement (see,             e.g., FIG. 7)             -   e.g., in the embodiment shown in FIG. 9A, a click on a                 mode transition button 902 (shown in this example as                 “19”) allows for a “lateral” or “horizontal” mode                 transition to “edit” (shown in FIG. 9B)         -   Traversing relationships (either cross-reference or             master/detail) is referred to as “drill-down” (and, upon             return, “pop-up”) or “vertical” movement across tables (and             nested stack contexts) (see, e.g., FIG. 9)             -   e.g., in the embodiment shown in FIG. 9B, a click on a                 “drill-down” button 904 (shown in this example as “State                 or Province”) allows for a “drill-down” to related                 detail records (shown in FIG. 9C)         -   Vertical navigation therefore always increases or decreases             the “stack depth”, while horizontal navigation merely alters             the “view” of the current table—affecting only the current             (bottom-most) stack level         -   Drill-downs are supported by enabling “hot-linked” (or             “clickable”) labels for the related data fields in the             primary table (stack context) (see FIGS. 9B and 9C)         -   A drill-down traversal “suspends” the above stack context         -   Drilling-down across a cross-reference relationship imposes             no “context constraints” on the lower stack context, while             drilling-down across a master/detail link constrains the             subordinate table to only those records “belonging” to the             above stack-context table-record (see, e.g., FIG. 9C), such             that:             -   A superseding filter is applied to all detail-table mode                 displays, separate from (and invisible to) any                 lower-context search-filters which may subsequently be                 applied by the user             -   Even a “full browse” request (with no explicit                 search-filter) therefore shows only related                 child-records             -   The title bar 912, 920, 926 (across all modes)                 separately indicates the subordinate-table context                 constraint with a “FOR <PARENT-TABLE> <PARENT                 RECORD>”-style suffix (vs. the “(FILTERED)” suffix,                 which indicates a user-applied search-filter). (For                 example, Title Bar 912 of FIG. 9C shows constraint from                 above stack context, Title Bar 920 of FIG. 9D still                 shows the context-constraint, and Title Bar 926 of FIG.                 9E reflects both the above context-constraint and the                 presence of a current-context “filter.”)             -   In Edit mode (for a specific child-table record), the                 user is prevented from changing the datum that links the                 child record to its parent record, by filtering the                 dropdown-list for the corresponding FK field so that it                 contains only the parent-record value         -   Full lateral movement (mode-switching) is supported within             the subordinate stack context         -   User can “return” (ascend the context stack) either by             “committing” a lower-level action (a database edit or             addition), or by abandoning the subordinate stack context             (via the context-stack display or table-navigation header).             In the former case, committed changes are automatically             propagated to the above stack context and displayed in the             corresponding mode display (i.e., “results” are “returned”)             unless the user has enabled POWER ADD in the lower context;             in the latter case, any pending changes are abandoned, and             the above stack context is restored exactly as originally             suspended         -   Cross-reference drill-downs are “context sensitive” to the             parent-field status: A drill-down from a blank parent-field             enters the subordinate stack context in “Add” mode, while a             drill-down from a non-blank parent-field enters the             subordinate stack context in “Edit” mode for the             already-selected (cross-referenced) secondary-table record.             Nevertheless, the default drill-down mode can be             “overridden” (that is, abandoned) via a lateral or             horizontal mode-switch in the lower stack context. In any             event (and regardless of intervening actions), a “committed”             return from a subordinate stack context will always properly             update the parent record         -   Master/detail drill-downs generally enter the subordinate             stack context in “Browse” mode, although this behavior can             be modified as a “business rule” via the described             customization mechanisms (see FIG. 9 and the             CreateSchema.sql script)         -   The user may always return directly to any suspended             (“higher”) stack-context by clicking on the corresponding             stack-display entry 908. Doing so effectively “pops” the             stack, and abandons any work-in-progress in all lower             contexts. (For the embodiment shown in FIG. 9C, for example,             clicking on “COUNTRY [EDIT]” abandons the current stack             content and restores the above context exactly as originally             suspended, i.e., as shown in FIG. 9B.)         -   The user may further search or filter records at the             subordinate stack context level by clicking on the “New             Search” link in Mode Navigation 910. In the embodiment             shown, the further search page (see, e.g., FIG. 90)             comprises the following screen elements:             -   STACK DISPLAY 914 which still shows the nested contexts             -   SEARCH FIELD 916. In the embodiment shown in FIG. 9D,                 search field 916 is free-form text entry, wherein the                 text “North” adds an additional “filter,” requiring that                 “State or Province Name” begins with “NORTH”.             -   TITLE BAR 920 which still shows the context constraint             -   SEARCH INITIATING BUTTON 918, which, when clicked,                 initiates a “lateral” or “horizontal” mode transition to                 (filtered) “browse” mode (see, e.g., FIG. 9E). The                 embodiment shown in FIG. 9E comprises the following                 screen elements:                 -   STACK DISPLAY 922 which still shows nested contexts                 -   TITLE BAR 926 which now reflects both the above                     context-restraint (as shown, e.g., in FIG. 9D) and                     the presence of current-context “filter”                 -   SCROLL NAVIGATION 924 allowing the user to navigate                     through all the records in a table and also allowing                     the user to dynamically change the number of records                     displayed. In the embodiment shown in FIG. 9E,                     manipulating the Scroll Navigation 924 has no effect                     because all the records under the current constraint                     and filter are displayed on one page, since only two                     rows now meet both parent-context constraint and the                     current “filter.”     -   Integrated, group-based security mediation, “granular” both in         scope (i.e., global-, table-, row-, or field-level) and by task         (browse, edit, add, delete), which dynamically adjusts all         system displays (throughout the entire UI paradigm) according to         the user's granted access-rights, such that prohibited options         are always hidden         Note, finally, that while the preferred embodiment operates         according to the particular paradigm described above, it remains         possible to effect alternate paradigms which would nevertheless         be consistent with the basic principles of the invention. For         instance, it may be desirable in some instances to realize         instead a “modeless” UI paradigm, such that all end-user         activities (browsing, searching, editing, adding) are supported         by a single, unified display context (such as a “spreadsheet”         display).

Software (written in Java and JSP, in the reference implementation) automatically and dynamically (“on-the-fly”) generates a fully functional UI system (written in HTML, Javascript, and HTTP/CGI in the reference implementation) based upon, and connected directly to, the underlying data model (as instantiated within the RDBMS), and in full conformance to the described paradigm. In order to generate the UI, the RDBMS is first interrogated or scanned by this software, applying a body of rules to interpret the data model (comprising its tables; their column-complements, datatypes, and constraints; and relationships across the tables), and to correlate same to the UI paradigm (either “on-the-fly”, or by building an in-memory representation, or “cache”, of said data model, and by automatically deriving enhanced back-end “views” of all tables, which are consistent with the paradigm and which, further, coherently incorporate any and all extensions, customizations, adaptations, or overrides which may have been specified as described below). In the reference implementation, the results of this RDBMS interrogation are used to construct an internal object representation of the schema, conforming to a graph in which the nodes represent database tables, and the edges represent relationships (i.e., referential integrity links) between these tables. As the UI is rendered for any given database table, this underlying object representation is referenced, and appropriate components for depicting and traversing all cross table links are automatically included in the resulting display.

A core complement of naming conventions and annotational methods (written in XML, in the reference implementation) is used for enhancing and extending the representation of the table structures and relationships (entirely within the back-end representation of the data model, in the reference implementation) so as to more fully support revelation of the schema structure through external interrogation. Said methods consist of “annotations” (or “comments”) which are “attached to” (or “associated with”) individual tables or table-columns within the back-end RDBMS; in discussing these methods, it is important to note that although there are any number of alternative embodiments for the formatting, storage, and association of such annotations with their corresponding objects—including (but not limited to): formatting as XML-tagged, name/value-paired, or fixed-sequence data; storage within native-RDBMS “comment” fields, application-defined database tables, or external (operating system) disk files; and association via native-RDBMS comment “attachment”, explicit object-naming (within the annotations themselves), or pointers or keys (attached to the objects themselves)—the methods ultimately concern the principles by which such embodiments may be designed and applied to illuminating the schema, rather than any particular configuration or embodiment itself. Within the reference implementation, then, the attachment of annotations, as XML-formatted “comments”, directly to database objects, should be considered illustrative of, rather than essential to, the methods so described. The core conventions and methods comprise:

-   -   The indication of column-datatypes not natively (or explicitly)         supported by the underlying RDBMS (for example, “binary” or         “yes/no” fields in the Oracle8i-based reference implementation)         yet subject to special handling within the UI paradigm, via the         use of specific object-name suffixes (“_FLAG”, in this example)     -   The specification of master/detail relationships between tables         (as distinguished from a [reverse-]cross-reference         relationship), by associating a table-level annotation with the         master (or “parent”) table, and indicating both the table name         and the parent-referencing FK field for each detail table (see         comments in the CreateSchema.sql script)

Following the paradigm, the generated UI comprises all mode displays for all tables, with integrated (-into-the-mode-displays) mechanisms for representing, navigating, and managing relationships across tables (comprising hierarchical context constraint/enforcement, and pass-through/“pop-up” return, or “propagation”, of subordinate-context results). In rendering this UI, the preferred embodiment applies logic to (re-) convert column- and table-names retrieved through RDBMS interrogation from all-uppercase text, if necessary (as it is with Oracle8i, in the reference implementation) into mixed-case, initial-caps text (where only the first letter of each word—or “token”—is capitalized), and to replace underscore characters with spaces. The case-restoration logic is designed to also consider a list of approved acronyms—or, more generally, “exceptions”—which, when encountered as tokens within object-name strings, are instead cased exactly as they appear in the list. (This could mean all-uppercase, all-lowercase, or any non-conventional mixture of cases, such as “ZIPcode”.) This case-exceptions list is provided once, globally, for the entire system, and impacts all table- and column-name references throughout the UI presentation. On the reference implementation, the list is defined as a string array within a public “CustomCaps” object; this object could in turn be initialized via a disk file, or a special database table.)

The software also constructs and utilizes the above-described hierarchical context stack for maintaining (and suspending) the working state of a particular table (comprising selected record, display mode, pending form-field entries, in-effect search-filter parameters, Browse-mode scroll position, and any filter constraints imposed from above stack contexts) while “drilling down” across relationships to work with related information (in a possibly constrained working context) and returning relevant changes to the parent-context table, and a corresponding UI convention for displaying and navigating this stack (see, e.g., stack display 906 in FIG. 9C, which displays the nested contexts). Note further that, in addition to its core function in supporting nested working contexts (and by virtue of its always being on-screen), the context stack also enables certain ancillary capabilities:

-   -   Since the current context (or “table-session”) always         corresponds to the “bottom” of the stack (i.e., the rightmost         link in the display), the user can “refresh” his current         table-session by clicking on this link. This can be useful, for         instance, when the user wishes to “undo” or revert numerous         changes made to a current Edit- or Add-mode form (but not yet         committed) without having to re-navigate to the current table         and record     -   When a system exception (security violation, internal error,         etc.) occurs, the resulting error screen also incorporates a         stack display. Although the default error-screen behavior is to         restart the user's session after a timed delay (and thereby         abandon all work in progress), the user will often be able to         recover his session by making a selection from the error-page         stack display

The preferred embodiment further provides a structured collection of methods, mechanisms, tools, techniques, and facilities for extending, customizing, adapting, or overriding the baseline UI paradigm and software to support non-standard and/or special requirements (“business rules”), comprising:

-   -   Means to “override” the default behavior for FK “display-name”         resolution with (either or both) “global” and/or “local” custom         specifications on how to generate display-names for a given         foreign-key:         -   Such overrides can be useful, for example, when the foreign             (referenced) table lacks a (resolvable) name column; when a             composite (multiple-field), treated, or otherwise modified             display-name is desired; when the sort-order within display             lists should be modified; or when the foreign-table records             depend on yet other table-records (foreign, in turn, to the             FK-referenced table) for full name construction (for             instance, where FKs into a “CITY” table depend in turn on             FKs from CITY into a “STATE” table in order to distinguish             like-named cities, such as Portland, Oreg. and Portland,             Me.)         -   A custom specification consists of an explicit SQL             expression that generates key-value/display-name pairs for             any and all foreign-table key values         -   Such specifications will automatically propagate throughout             the entire UI, including all relevant Browse-mode cells and             Add/Edit/Search form-fields         -   Global display-name specifications are associated as             table-level annotations (see above) with the referenced             foreign table         -   Local specifications are associated instead as column-level             annotations with the referencing (foreign-key) column in the             base-table itself         -   In this way, both “default” (global, or system-wide) and             “special-case” (local, or single referencing-table only)             custom display-names can be defined for the same foreign             table. If a “local” specification is defined for a given             FK-column, it will supersede any “global” or “default”             specification also defined for the referenced (foreign)             table.         -   In the reference implementation, specifications are made via             a special XML tag (“<sql>”) which is attached to the table             or column (for global or local specifications, respectively)             as a “comment”     -   Ability to alter the order and visibility of individual         table-columns across all mode displays (Browse, Add, Edit,         Search) vs. the actual column-complement and -ordering of the         associated (underlying) table:         -   This is sometimes desirable in a post-production             environment, especially when the particular back-end RDBMS             product in use makes it impractical or impossible to alter             the actual structure of the underlying table once it has             been populated with data and is participating in             referential-integrity relationships with other populated             tables         -   A specification consists of a listing of the desired             table-columns, in the desired display order (either by name             or, alternatively, by ordinal position in the actual             underlying table)         -   If a specification is made, then any columns not explicitly             included within that specification will be suppressed from             the UI mode displays         -   Specifications are associated as table-level annotations             with the actual underlying table         -   In the reference implementation, specifications are made via             a special XML tag (“<columnOrder>”) which contains sub-tags             (“<cl>”) indicating the desired columns in order and by             name, and is attached to the table as a “comment”     -   Support for composite or “custom views” of multiple-table data         which mimic a single base-table. Such a derived (non-table)         result-set is typically generated by a “stored query” or “SQL         VIEW” within the back-end RDBMS, and nevertheless can be         rendered and presented by the UI as if it were an actual single         base-table (subject to certain limitations which may be imposed         by the underlying RDBMS—particularly, the inability to edit or         add “records” for such result-sets, rendering them effectively         “read-only”)     -   Ability to manually define Search-mode “dropdown fields” (which         list the range of possible values for a given column) for such         custom views:         -   Because, by its nature, the custom view appears to be an             actual table—and therefore obscures the underlying (real)             tables on which it is based—the system cannot automatically             resolve the referential-integrity (RI) links that would             normally serve to identify the appropriate value lists             (i.e., foreign-table values)         -   Moreover, the normal value-to-key translations managed by             dropdown fields are inappropriate for custom views anyway,             since these views actually incorporate the cross-referenced             values themselves (rather than foreign keys that point to             these values, as base-tables do)         -   To support custom-view dropdown lists that (appear to)             behave consistently with the general (actual-table) UI             paradigms, then, a manual (explicit) dropdown-list             specification is made for each corresponding custom-view             column         -   A specification identifies the foreign table which contains             the dropdown-list values, and the column (either by name or,             alternatively, by ordinal position within that table) which             supplies the actual values         -   Specifications are associated as column-level annotations             with their corresponding custom-view columns         -   In the reference implementation, specifications are made via             a special XML tag (“<manualDropDown>”) which, in turn,             contains sub-tags indicating the related foreign-table name             (“<foreignTableName>”) and key field (“<foreignKeyField>”),             and is attached to the corresponding view-column as a             “comment”     -   In-place pass-through (drill-down) from custom views to         Edit-mode displays for underlying (component) base-table         members:         -   Because the “stored queries” or “SQL VIEWS” that underlie             custom views are typically non-updateable (according to             RDBMS limitations), the usual UI mechanisms for editing data             cannot be used with these views. Nevertheless, it is often             desirable to provide users with easy access to editing for             (at least some of) the data behind the views         -   To enable such editing access, a mechanism is provided to             create a (series of) cross-referential link(s) from the             individual cells (row-values) in a given column of a             Browse-mode display, with each link forwarding the user to a             secondary display—most commonly, to an Edit form for the             underlying base-table containing that cell's value (although             it is, in fact, possible to link-through to any arbitrary             table, row, and column, and in any “mode”)         -   While such links usually reference the same underlying             base-table (and -field) for every row in the column,             special-case extension logic can reference different tables             for different rows, according to “trigger” or “switching”             values from another column in that same display-row         -   A further variation of the mechanism (described below)             modifies the behavior of the leftmost-column “row label”             links, rather than the interior Browse-mode table-values             themselves         -   On-screen, the link appears as a highlighting (in the             reference implementation, a “clickable link” or HTML “HREF”)             of the cell-value itself. (Empty cells display the value             “NONE” so as to still enable drilldown navigation.) When the             user selects (clicks on) the link, the display forwards             (typically) to an Edit form for the corresponding record in             the appropriate underlying base-table, with the proper             edit-field pre-selected (i.e., given the “focus”). In             effect, the system auto-navigates to the same exact             base-table Edit form, selected-record, and edit-field that             the user could (theoretically) navigate to himself,             manually, in order to alter the underlying datum that             supplies the custom view         -   The working context for this drilled-down Edit form is             constrained by the same mechanisms that govern master/detail             drilldowns (as described above)—that is, a stack-context             filter is imposed on the edit session in order to prevent             the user from changing the datum that links the base-table             record to the custom view (note that this also requires a             separate, explicit specification of the base-table as a             “detail table” to the custom view); and if/when the user             “commits” the drilled-down edit session (by pressing the             “Update” button), she is automatically returned to the             “parent” custom view         -   A specification identifies the underlying (or “target”)             base-table; the (initial) base-table display-mode             (typically, “Edit”); the custom-view column whose             corresponding row-value contains the identifying key for the             target base-table record; the custom-view column (if any)             whose corresponding row-value contains the “constraining”             (master/detail) key; and the base-table field-name which             should be selected (i.e., the field that contains the target             value, and should therefore receive the “focus”)         -   Specifications are associated as column-level annotations             with their corresponding custom-view columns         -   A special-case extension of the specification can be             associated as a table-level annotation with the custom view             itself (rather than one of its columns). In this context,             the specification will modify the behavior of the             leftmost-column “row label” links (which, in normal-table             Browse-mode displays, link to Edit-mode displays for the             corresponding table-records). A common use for such             specifications is to support master/detail-style transitions             to secondary Browse-mode displays of records which “belong             to” the selected custom-view record         -   In the reference implementation, specifications are made via             a special XML tag (“<customDrillDown>”) which, in turn,             contains sub-tags indicating the target base-table             (“<tableName>”), display-mode (“<mode>”), identifying-FK             field within the custom view (“<keyColumn>”),             constraining-context or master/detail key, if any             (“<parentColumn>”), and target field (“<focusField>”), and             is attached to the corresponding view-column as a “comment”

The preferred embodiment also supports the specification and enforcement of both global and granular (by table and function) access rights and activity-stamping, according to a group-based (rather than hierarchical) permissions scheme, and based on table entries which themselves can be entered and maintained via the system:

-   -   In the reference implementation, six tables support these         security features: PEOPLE, USERS, SECURITY_TABLE,         SECURITY_GROUP, SECURITY_GROUP_USERS, and SECURITY_GROUP_TABLE:         -   The PEOPLE table contains an Active_Flag field, which allows             for “deactivation” of individuals without destroying             existing RI links throughout the database. Every system user             must appear in the PEOPLE table (among other reasons, to             support full-name resolution when displaying usage-tracking             fields through the UI), and if/when a user's             PEOPLE.Active_Flag is turned off, the user is immediately             blocked from all further system access         -   The USERS table incorporates (among others) a Login_ID             field, which is correlated against the system-user's             operating-environment credentials. (In the reference             implementation, this is the UID which has been authenticated             and forwarded by the web server; alternatively, it could be             the user's OS login.) When the system establishes a new             user-session (upon the user's initial contact), it attempts             this correlation to a valid USERS.Login_ID. If no             correlation can be made, access to the system is denied;             otherwise, the corresponding USERS.Users_Key value is             henceforth associated with that user's session         -   SECURITY_TABLE maintains a list of all security-mediated             tables and custom views. (Alternatively, this list could be             automatically derived from the system's data-model             interrogation; the use of an explicit and hand-managed table             supports the manual exclusion of “special” or “hidden”             tables and/or views)         -   SECURITY_GROUP supports the definition of functional             security roles. In and of themselves, entries to the             SECURITY_GROUP table are little more than descriptive names;             their primary purpose is to serve as “connective conduits”             between USERS and SECURITY_TABLEs. It is important to note             (again) that SECURITY_GROUPs are non-hierarchical; that is,             each group can be granted any mix of rights to any arbitrary             set of tables, without respect to the rights of other             groups. And USERS can be assigned to any number of             SECURITY_GROUPs; When a user belongs to multiple groups, her             aggregate rights comprise a superset of the rights for each             of the groups to which she belongs         -   SECURITY_GROUP_USERS simply effects many-to-many             relationships between USERS and SECURITY_GROUPs, and is             defined (via the methods described above) as a “detail”             table to both of these         -   Similarly, SECURITY_GROUP_TABLE supports many-to-many             relationships between SECURITY_GROUPs and SECURITY_TABLEs             (and is a “detail” table to both). Additionally, however,             the SECURITY_GROUP_TABLE incorporates Boolean (true/false)             columns which indicate permission for the related             SECURITY_GROUP to (respectively) browse, add to, edit, or             delete from the corresponding SECURITY_TABLE. This forms the             nexus of access-rights control     -   All UI displays automatically adjust to the current user's         access rights. In particular, the following navigational         elements (“links”, as defined in the reference implementation),         appear or are suppressed according to the user's rights:         -   Mode-navigation bar links 710 (browses/searches/add); here,             suppressed links are entirely removed from the display,             rather than simply “disabled” (or made “non-clickable”, as             is done for all other links, below)         -   Record-edit links 706 (in the first column of Browse-mode             displays)         -   Drill-through cross-reference links (on the labels of             Add/Edit/Search dropdown fields)         -   Drill-down master/detail links (on the labels of Edit-form             master/detail summary-counts)     -   Note that custom views with custom-drilldown specifications are         subject to “double” security mediation: If edit permission to         the custom view itself is withheld for a given user, then all         custom-drilldown links will also be disabled. But (even) if the         custom-view edit permission is granted, the user must also have         the necessary rights to support each particular drilldown (e.g.,         edit or browse permission on an underlying table) before the         corresponding link will be enabled     -   Separately (and assuming the necessary access rights have been         granted), all system add/edit activity can be time- and         user-stamped at the table-record level (optionally, on a         per-table basis). Security-stamping is completely automatic, and         is governed (in the reference implementation) by the presence of         four special columns within the table: Entered_By_Users_Key,         Entry_Date, Modified_By_Users_Key, and Last_Modified_Date. If         these columns exist, then any “add” event causes the current         USERS.Users_Key (from the user's session) to be recorded in both         the Entered_By_Users_Key and Modified_By_Users_Key columns, and         the current system time to be stamped into both the Entry_Date         and Last_Modified_Date columns. “Edit” events, of course, update         only the Modified_By_Users_Key and Last_Modified_Date columns.         Note further that when they exist in a table, these fields are         visible only in Browse and Search displays; they are hidden (but         automatically updated) from Add and Edit displays     -   Although not present in the reference implementation, the         granularity of this model can be readily extended with both row-         and column-level access mediation:         -   ROW-LEVEL SECURITY allows for the individual rows (records)             of any given table to be made visible or invisible (and,             therefore, accessible or inaccessible) to a given user:             -   In a sense, row-level security can be said to affect                 only “content” visibility, rather than “structural”                 visibility (as with other security axes); a row-level                 security filter impacts which particular table-entries                 are presented, but never which classes or types of data                 elements             -   A specification thus identifies the filter condition                 (i.e., WHERE clause) that relates one or more                 table-columns to (some transformation/JOIN-sequence on)                 the current user. (Note that such “user relations” may                 optionally involve attributes of the particular user,                 and/or those of “security groups” to which the user                 belongs)             -   Specifications are associated as table-level annotations                 with the actual underlying table             -   Because there are no effects upon the structure or                 “shape” of the data, these filters can be                 “encapsulated”, effectively, and introduced as a                 (logical) “shim” layer between the raw back-end tables                 and the data-dictionary object model.             -   By exploiting the identical column structure of each                 such “shim view” to its underlying base-table, on the                 one hand, and to the “virtualized” schema view (as                 constructed during the interrogation phase) of that                 table, on the other, the rest of the system logic and                 infrastructure can be insulated from any awareness of                 (or sensitivity to) this mechanism             -   Application of the row-level filter consists of                 “surgical” modifications to the defining SQL for the                 corresponding Browse-mode view (see above), so as to                 incorporate the requisite additional WHERE clause (and                 any additional FROM-clause tables, utilizing the same                 view-integration and alias-merging logic already                 employed within the reference implementation in                 generating said view)             -   Function-oriented mediation (i.e.,                 Browse/Edit/Add/Delete granularity) is supported via                 (optional) separate specifications (per table) for each                 function (and with a “default/override” hierarchy among                 these specifications—such that Browse rights obtain for                 editing, for instance, unless explicit Edit rights have                 been specified). The UI-generation logic then compares                 record-presence across the respective (resulting) views                 to resolve specific rendering and action decisions                 (i.e., is this record editable?)         -   COLUMN-LEVEL SECURELY allows user access to be governed on a             field-by-field basis:             -   Specifications are analogous to those described in the                 reference implementation for table-level security (see                 the discussion of SECURITY_GROUP_TABLE, above), except                 that only “Browse” and “Edit” rights are meaningful on a                 per-column basis (that is, there is no way to “Add” or                 “Delete” only individual columns)             -   Column-level specifications are treated as “subtractive                 overrides” to table-level specifications, such that                 table-level specifications serve as “defaults” that can                 be further restricted—but not expanded—by column-level                 specifications             -   Application of column-level security to the Browse                 function consists of an additional “overlay” view which                 hides additional columns as necessary             -   Edit-function mediation is processed by the UI on a                 per-field basis, either (or both) during rendering                 (where display conventions utilize read-only fields, or                 otherwise signal non-editability via labeling                 conventions [such as italicized text]) and/or processing                 (where attempts to change non-editable fields are                 rejected, with an alert notification to the user)

Also incorporated into the preferred embodiment are both generalized and special-case exception-handling mechanisms, with integrated session-recovery support:

-   -   The generalized exception-handling mechanism guarantees a         controlled recovery from any unanticipated error condition. This         mechanism:         -   Presents as much diagnostic information as possible, within             a paradigm-consistent UI display, comprising:             -   A pass-through errortext from the underlying                 program-execution environment             -   A complete “(program call-) stack dump” indicating the                 suspended (and nested) program-function calls in effect                 at error-time             -   The entire current context-stack display         -   Permits user recovery either by:             -   Controlled reinitiation of a(n entirely) new session             -   Navigation through the context-stack display to a                 pre-error session context, thereby (generally) enabling                 the user to recover his session-in-progress                 (more-or-less) intact, vs. requiring a restart from                 scratch     -   Special-case exception-handling mechanisms are defined         separately for certain types of system errors which are common         or “normal” (such as authorization failures or session         timeouts). In such cases, these “customized” exception-handlers         can suppress unnecessary technical detail (which can be         confusing or alienating to end-users and give the misimpression         of software failure), and provide additional (end-user suitable)         information specific to the user's particular error context. The         reference implementation can identify and separately handle the         following common exceptions:         -   SESSION-SEQUENCE ERRORS: In the reference implementation             (which, again, is web-based), it is important that the             system govern the “flow” or sequence of pages passed back             and forth between the (web-) server and the client             (web-browser); as a result, the system incorporates several             mechanisms to track and enforce this flow (comprising             back-button “defeat” logic, and incremental serialization of             all URLs [such that the system always knows what serial             number to “expect” along with the user's next             page-submission]). If the user manages to violate this flow,             either intentionally or inadvertently (perhaps by selecting             a “favorite” or “bookmark”, or by clicking multiple links on             the same page before the server can respond), the system can             detect this particular error, provide a detailed explanation             of how and why it might have occurred, and (per above) allow             the user to recover her session-in-progress without any loss             of work         -   SECURITY VIOLATIONS: Generally, the system proactively             prevents the user from attempting access to any authorized             system modes or functions. However, in the (web-based)             reference implementation, it is not impossible for the user             to navigate to a situation where he might possibly attempt             an illegal transition—or to manually adjust a URL so that it             attempts such unauthorized access without triggering a             session-sequence error (as described above). In these             cases—and in the simpler case, when a user attempts access             without any system rights whatsoever—the system provides a             plain-English report of exactly what access rights the user             has tried to violate         -   SESSION TIMEOUT: Because the system maintains a “user             session” in which various context, sequence, and             configuration information is tracked, and which (because it             consumes system resources) can expire after a (configurable)             period of disuse—and also because (in the web-based             reference implementation) the dialog between client and             server is “connectionless” (meaning that there can never be             any automatic detection by the server that a user has “quit”             or “broken” a connection)—it is entirely possible that a             user may try to continue or resume a session which appears             perfectly intact from his perspective (i.e., in his             web-browser) but for which the system has discarded the             corresponding user-session. In this case, a full             session-reinitiation is still required—but it can at least             be delivered along with a meaningful explanation of what has             occurred     -   These special-case error handlers dovetail and integrate         smoothly with the generalized exception-handling facility, and         share many of the same features (including, when available, the         session-stack display). Within the reference implementation,         these handlers are hard-coded, but they describe the basis of a         subsystem which can be readily extended—abstractly and         dynamically—in several ways:         -   Specific exceptions—and their corresponding, customized             error displays—can be defined and administered via a central             list (or table), and automatically detected (and their             respective displays invoked) at runtime, within the             framework of a generalized facility and without the need for             custom programming         -   Information can be “mined” from the pass-through             errortext—and, potentially, from the runtime environment as             well—according to the nature of the particular error, and             used (if appropriate) in the construction of dynamic error             displays (via templates, for example)         -   Custom follow-on actions can be associated with specific             errors, so that special-case recovery procedures can be             specified. (For instance, a database-detected data-entry             violation might cause a return to the previous data-entry             form.) “Mined” runtime-environment information can also be             used here to govern the behavior of said follow-on actions

A generalized, extensible, and data-driven “pop-up help” facility is also included in the reference implementation. This facility allows for the specification of descriptive text which can be associated both with specific on-screen navigational elements, and with (any) individual schema elements (i.e., table-columns). When the user positions his mouse over a described object (or data-field) and pauses for a specified timeout interval, the system will flash a pop-up window (or “balloon”) displaying the corresponding description. The system thereby becomes self-documenting with respect to both the UI paradigm itself, and the meaning of its data-fields. Within the reference implementation, the specifications are stored within back-end tables—so that they, too, may be administered via the system UI—although any of the above-described annotational methods could alternatively be used.

Except as noted, the detailed implementation of each of the foregoing capabilities is set forth in full in the accompanying source code, which represents the complete source code for a working version of the reference implementation. A full demonstration RDBMS schema upon which this system can operate has been provided, and accompanies this application and is incorporated herein by reference (see FIG. 5 and the CreateSchema.sql script).

Numerous extensions of the above-described scheme are of course possible:

-   -   Most importantly, while the reference implementation is in         various instances custom-coded to the data-dictionary         architecture of its particular underlying RDBMS (i.e.,         Oracle8i), the scheme is nevertheless readily converted to a         “generic” (or “RDBMS-agnostic”) architecture through the         introduction of a platform-neutral “middleware” layer. (The         DatabaseMetaData class within the Java 2 Platform Standard         Edition v1.3.1 API Specification, for instance, is easily         applied toward this end.) The described invention, therefore, is         by no means limited to a specific RDBMS product     -   A set of mechanisms, rules, and methods may be provided through         which each end-user can evolve (and manage) personalizations to         the UI architecture (with persistent back-end storage and         tracking by user and/or group)—including (but not limited to)         preferred table-navigation hierarchies; UI “entry points” based         on usage-frequency patterns; default (or most-recent)         searches/filters for each back-end table: default “page size”         for Browse-mode lists (adjusted for the particular user's screen         resolution, for example); default sort-orders for each table;         and default “Power Edit” and “Power Add” settings. Because         user-tracking is already integrated (for security purposes), it         is a simple matter to add the supporting tables and         UI-application “hooks” to collect, store, and utilize such         preference information     -   Expanded concurrency-control options are easily incorporated         into the scheme. Many database-related systems offer a range of         behaviors which extend from unfettered write-back of edited         table-records (offering maximum system performance, at the cost         of minimal overwrite protection), through competing-update         detection with approval/abandonment of data overwrites (a blend         of performance and protection, at the cost of added complexity),         to full edit-record locking (offering maximum protection at the         cost of performance); and while the reference implementation         incorporates only the first of these behaviors, the others can         certainly be added—along with a system-configuration mechanism         for choosing among them—in a straightforward manner     -   A generalized journaling/auditing subsystem may also be         integrated. Such a subsystem could, for instance, utilize         database “triggers” to update a master table with a new tuple         (comprising table-name, record-key, column-name, old-value,         new-value, user-key, and timestamp) whenever any table-record is         modified. Such a mechanism would (at a cost in system         performance, of course) permit complete backtracking/“rollback”         to previous database states, and guarantee the ability to         recover from any rogue data modifications (whether accidental or         malicious) and identify the actors     -   A further extension to journaling/auditing support is the         ability to require a user to explain his justification for         (only) certain data-field changes, and then either record that         explanation to the system journal or audit log (along with the         other tuple information), or (possibly) roll-back the         transaction (if the user declines to supply an explanation).         Such a facility could be implemented with additional text-entry         fields integrated into the primary Edit-mode display, or         alternatively, with “pop-up window” logic (which, within World         Wide Web presentation, could comprise additional browser windows         or DHTML “simulated” pop-ups, for instance). The specification         of which data-fields should require such justification would be         considered a “business rule”, and could be implemented via any         of the annotational methods described elsewhere in this         document. Such specifications could also be assigned at various         levels of global vs. local “scoping” (i.e., perhaps         automatically for all date fields, or only for specifically         assigned text fields)     -   Within the current (World Wide Web-based) reference         implementation, it is possible to select certain navigational         links (for example, from the context-stack display or the         mode-navigation bar) which will abandon the user's current         screen display and, with it, any data entries or modifications         which may have been made but not yet committed to the database.         Although this behavior is by design, it may be desirable to add         a pop-up “warning” mechanism for such cases, so as to alert the         user to the imminent loss of data (and to provide a means for         aborting said action). Such a mechanism could utilize         client-side Javascript logic to:         -   Set an internal flag each (and every) time any on-screen             change is made         -   Invoke a “cover function”, each time a screen-abandoning             link is clicked, which will display a confirmation dialog             (pop-up window) if the “change flag” has been set (or, if             the flag is not set, will simply execute the link)         -   Proceed with the link action (and abandon the current             screen) only if the user supplies explicit confirmation     -   A variety of extensions can be made to the Browse-mode display         paradigm, comprising:         -   The ability to sort Browse-mode listings (by any combination             of columns) by clicking on the corresponding             column-headings. Successive clicks on the same             column-heading would invert the sort-order for that column;             successive clicks on different columns would effectively             produce “ordered sorting” (where the most-recently clicked             column is the “primary” sort, and each successively             less-recently clicked column is the next “subordinate” sort)         -   Support for “random-access” page navigation, wherein the             table-header (which, in the reference implementation, allows             direct entry only for the number of rows per page) would             also allow direct entry of the desired page number. For             instance, a Browse-mode display whose table-header said             “PAGE 5 OF 12 (TOTALING 300 RECORDS AT 25 ROWS PER PAGE)”             would thus render both the “5” and the “25” as text-entry             fields, so that in addition to resizing the page length (by             changing the rows-per-page entry), the user could also             “zoom” to a specific page just by changing the page-number             entry. This would eliminate the need to scroll,             page-by-page, from either the top or bottom of the             result-set         -   Similarly, another form of random-access page navigation             could be introduced via the addition of phonebook-style             “tab” links (for instance, “A|B|C|D . . . ”) such that             clicking a particular link would jump to the first record in             the result-set whose corresponding-column entry began with             that character:             -   Said “corresponding column” could be (initially)                 determined according to similar default-processing rules                 to those embodied in the reference implementation for FK                 display-name resolution (for instance, the first column                 whose name ends in “_NAME”, if any)             -   Alternatively, the corresponding column could simply                 track the current (primary) sort-order column (as                 described above), if implemented             -   Yet another option would be to allow explicit                 designation of the corresponding column via an                 associated dropdown-list of all table-columns             -   However selected, any change in the corresponding column                 would then automatically regenerate the tab list,                 according to the range of actual (sorted) leading                 characters appearing within that column. In this way,                 numeric tabs would appear for a “social-security number”                 column, vs. alphabetic tabs for a “last name” column     -   A variety of extensions can be made to the Search-mode display         paradigm, comprising:         -   In the reference implementation, field-value filters are             applied by default as prefix matches (i.e., as “starts with”             comparisons), with optional support for explicit             relational-operator prefixing (comprising <, <=, >=, >, and             exactly =). Relational options could be further extended to             support ranges (“between x and y”),NULL/NOT-NULL conditions,             and other arbitrarily complex transformations on the             corresponding field-values (such as field-value substitution             into a complex string-manipulation or arithmetic expression)         -   The reference-implementation Search-form paradigm comprises             a single set of fields (corresponding to the underlying             table-columns), where any entered filter-values (for the             respective columns) are logically “AND”ed together. A more             general and flexible search facility could:             -   Allow toggling between logical “AND” and “OR”                 combination of a search form's filter-values             -   Allow “stacking” of multiple search-form copies, such                 that the fields in each individual (sub-) form comprise                 a parenthetical filter “phrase”, which is “AND”ed or                 “OR”ed together (selectably, as above) with the                 parenthetical phrases for other sub-forms     -   A variety of extensions can be made to the Edit-mode and         Add-mode display paradigms, comprising:         -   In the reference implementation, violations of any extant             “unique” constraints on underlying table-columns are             intercepted and reported only upon violation, and then only             via the generalized exception-handling mechanism (in             response to a back-end RDBMS exception “throw”).             Alternatively:             -   Special-case exception handling (as described above)                 could still exploit the thrown back-end exception, but                 provide clearer diagnostics (i.e., exactly—and only—the                 field-value that has violated a “unique” constraint),                 and then restore the data-entry form with the                 problem-field contents pre-selected; or             -   Employ separate database-interrogation logic for each                 “unique”—constrained field, so as to “pre-qualify”                 data-entries—and, thereby, allow for “in-place”                 duplicate-entry detection and signaling (without ever                 leaving the data-entry form, and without invoking formal                 exception-handling mechanisms)         -   Similarly—but more generally—violations of any arbitrary             “check” constraints (such as imposed value-ranges, or             required satisfaction of algebraic expressions) are             intercepted and reported only upon violation within the             back-end RDMBS. Instead, such constraints could be extracted             from the back-end and “projected” into the client-side UI             display (for the reference implementation, via             custom-generated Javascript routines). Doing so would allow             the detection and signaling of constraint violations             immediately upon data-entry, without (additional) contact             with the back-end RDBMS (and this, in turn, would obviate             the need for any display/session recovery logic)         -   When adding new records, the reference-implementation             Add-form logic does not “initialize” fields for which the             back-end defines “default” values—that is, although the             underlying table-column will (properly) be set to its             default value if the corresponding Add-form field is not             explicitly set, the user has no indication (prior to             committing the new record) of that default value. Instead,             the form could automatically pre-populate the appropriate             fields with their corresponding default values (as             determined through interrogation of the underlying             column-constraints)     -   In certain situations, it may be desirable during schema         interrogation to “deduce” relational interdependencies between         tables where no explicit referential-integrity constraints have         been defined. In such cases, it is possible to further compare         field-names and associated attributes across tables, so as to         identify columns which (for instance) are identically named, and         (only) one of which is the primary key for its respective table.         Under these conditions, it could (optionally) be assumed that         the other-table column is a foreign-key cross-reference to the         first column. Note that, in so doing, the UI paradigm would then         enforce referential integrity for this relationship, even absent         the explicit back-end constraint.     -   Additional mechanisms for further customizing or adapting the         baseline UI paradigm and software to meet non-standard and/or         special requirements (“business rules”) are also indicated, such         as:         -   Specification and enforcement of correlations, interactions,             or interdependencies between disparate data-elements (either             within or across base-tables), comprising:             -   “Context-sensitive dropdown controls”, whose                 dropdown-lists are filtered (or “constrained”) based on                 user-defined relations to superior stack-contexts (other                 than direct master/detail constraints, which already are                 included as a part of the core UI paradigm). Such                 controls could be specified via any of the                 aforementioned annotational methods. Specifications                 would “attach” to the subordinate-level table-column                 (i.e., the column whose dropdowns should be “filtered”                 or “sensitized”), and would consist of tuples indicating                 (at least) the superior-level table, relevant                 table-column, and a relation between the superior and                 subordinate columns. Each tuple could (optionally) be                 further qualified so as to “scope” the relation—for                 instance, so that the filter should consider only so                 many levels above the current stack-context, or that the                 filter only applies if certain other tables also do (or                 do not) appear in intervening levels—and possibly, even,                 only in a specific sequence. It would also, of course,                 be further possible to assign multiple such                 “sensitivities” to the same target-column. Consider, as                 an example, a project-management schema, in which both                 equipment and technicians are assigned to projects;                 technicians have specific equipment certifications; and                 schedules apply both to projects and to technicians. In                 assigning new technicians to a given project, one may                 wish to automatically “pre-qualify” the dropdown-list of                 available technicians such that it only includes                 technicians who are certified on (at least some of) the                 project's equipment, and who also are currently                 available during the lifetime of the project             -   “Interactive dropdown controls” are similar, but effect                 relations between multiple elements within a single                 mode-display, rather than across context-stack levels.                 Using the above example, a single many-to-many table                 might connect technicians to projects; if the table is                 accessed directly (that is, at the topmost stack-level,                 rather than by drilling-down to it from the associated                 project record), then each time the “project”-dropdown                 is altered, the “technician” dropdown-list would be                 automatically regenerated according to the                 above-described criteria. Again, (potentially multiple)                 specifications per target-column would resemble those                 for context-sensitive dropdowns, except (of course) that                 the “superior-level table” and “scoping extensions”                 would be irrelevant here. Note that although these two                 dropdown-types are similar—and that, in some cases                 (namely, where context-sensitive dropdowns utilize only                 direct drill-down relations), the former could be                 simulated with the latter—each offers (or lacks)                 functionality which makes it more suitable for certain                 types of use             -   “Context-sensitive and interactive column-level                 security” would allow data-entry fields to “lock” (or                 unlock) according to values of (and changes in) other                 data-fields (for instance, once a project has reached a                 certain “status” designation). Again, specifications                 could be effected via any of the aforementioned                 annotational methods, would “attach” to the “target”                 table-column (i.e., the column whose security is being                 mediated), and would resemble those for                 context-sensitive and interactive dropdowns,                 respectively, except that the “relation” specification                 would be supplanted by a Boolean evaluation on the                 controlling data-field. Note that this same mechanism is                 easily generalized further to support the toggling of                 arbitrary column-level constraints (by adding a                 “constraint definition” field to the specification                 tuple).         -   Triggering of custom software subprocesses—on the front-             and/or back-end—under specified data conditions and/or at             specified system-transition events, such as the “data-change             justification” pop-up mechanism described above in detail     -   Various mechanisms for enhancing web-client (or client/server)         user-interface performance and functionality can be introduced,         comprising:         -   “Buffered” dropdown controls, which maintain their own             separate connections to the back-end RDBMS, and allow the             screen display to be rendered before their dropdown lists             have been completely populated. Such dropdowns can further             be made “typeable”, so that a user could begin typing a             desired value and “home-in” on matching list-entries; in             this case, list-retrieval from the RDBMS can by dynamically             revised to retrieve a successively smaller (i.e.,             closer-matching) result-set.         -   “Caching” or “sharing” of duplicate dropdown lists, when             such lists are lengthy and their retrieval significantly             impacts front-end performance and network traffic. For             instance, the user-stamping fields described above             (Entered_By_Users_Key and Modified_By_Users_Key) generally             appear together within the same tables, always share             identical dropdown lists, and can (potentially) grow quite             long over time; logic to retrieve the shared list once from             the RDBMS—rather than twice—for use within both dropdown             controls can effect meaningful gains in system             responsiveness.         -   “Back-link” support, to provide functionality similar to             that of the standard web-browser “back” button, but without             violating the integrity of the user-session or the             hierarchical context stack.         -   “Bookmarking” support, to provide compatibility with             standard web-browser “bookmarks” or “favorites” functions:             By clicking a special button or link, users can re-render             their current display with a re-formed URL, which completely             describes the current user-session and context-stack (or,             alternatively, a limited and “cauterized” subset of same) so             as to allow bookmark-based return to an equivalent display             at a later date.     -   Although the preferred embodiment comprises a stand-alone         application which interacts (on a client/server basis) with a         back-end RDBMS, it may in some circumstances become desirable         instead to integrate some or all of the invention directly into         said RDBMS product (or a tightly-coupled extension or utility to         same). Of course, any such alternative embodiment would still         conform to the principles of the described invention.

Finally, the implementation described herein could be further varied in numerous respects, but still be within the principles herein illustrated. For instance, while the reference implementation uses a World Wide Web presentation mechanism, a more conventional client-server or native-GUI system could instead be delivered. Also, while the reference implementation depends on adherence to certain structural requirements and naming conventions in the design of any underlying or “target” schema (comprising the use of a single unique, auto-generated primary-key field for every table; the existence of a supporting “sequence” [i.e., reference-implementation RDBMS mechanism for auto-generating primary keys] for every table, and that each sequence be named for its corresponding table plus a “_SEQ” suffix; the reservation of “_VIEW”-suffixed names across the entire table/view namespace [for use by auto-generated system views]; the use of certain column-name suffixes as alternatives to or substitutes for direct datatype- or other attribute-driven discovery [such as a “_FLAG” suffix to connote “yes/no” or “binary” fields, or a “_DATE” suffix to indicate time/date data]; and a specific complement of security-related tables, as described below), such requirements and conventions can be easily supplanted; circumvented, or removed, and do not in any way define or limit the scope of the invention.

RUN-TIME ENVIRONMENT FOR THE SCHEMALIVE REFERENCE IMPLEMENTATION

Overview

The Schemalive Reference Implementation (SRI) is a web application which conforms to Sun Microsystems' PEE (Java 2 Enterprise Edition) Platform, which in turn incorporates the JSP (Java Server Pages) 1.2, Servlet 2.3, and JDBC (Java Database Connectivity) 2.0 specifications on which the SRI explicitly depends. More information on the structure of web applications can be found at http://jcp.org/aboutJava/communityprocess/first/jsr053/index.html. The web application can be placed in any J2EE-compliant container (i.e., application-server software), including such products as BEA WebLogic, Macromedia JRun, and Apache Tomcat.

Directory Structure

A root directory named Schemalive is required; the system's JSP files and static content (i.e., images) are located in this directory. A subdirectory Schemalive/WEB-INF is also required, and must contain a file named web.xml, which is the deployment descriptor (see below) for the application. Supporting classes for the JSP are located in a subdirectory Schemalive/WEB-INF/classes. The web.xml references the application's custom tag libraries (see below) through tag library descriptor files. These XML descriptors are located in a subdirectory Schemalive/WEB-INF/taglib, and have a .tld ile extension. Following is a tree diagram for the SRI directory structure:

+Schemalive −AddEditForm.jsp −BalloonHelp.jsp −Browse.jsp −DataDictionary.jsp −DoAddEdit.jsp −DoViewGenerator.jsp −Error500.jsp −ExpiredSession.jsp −OutOfSequence.jsp −showSession.jsp +common −EmptyParamCheck.jsp −EntryPoints.jsp −GlobalFooter.jsp −GlobalHeaderHTML.jsp −GlobalHeaderJavascript.jsp −GlobalHeaderVARS.jsp +images −logo.gif −logo-width.gif +WEB-INF −web.xml +classes −Connection.properties +common −Debug-class +dbUtils −CustomCaps.class −CustomDrillDown.class −CustomDropDown.class −CustomDropDownComponent.class −DataDictionary.class −DataDictionaryServlet.class −DataDictionaryTD.class −MasterDetail.class −MasterDetailServlet.class −SQLUtil.class −TableDescriptor.class −ViewGenerator.class +HTMLUtils −Balloon.class −BalloonHelp.class −TableDescriptorDisplay.class +sessionUtils −ManageSession.class −StackElement.class −StackTag.class −StackTagExtralnfo.class +tagUtils −ViewTag.class −ViewTagExtralnfo.class +taglib −stack.tld −view.tld

Deployment Descriptor

The deployment descriptor (web.xml) is an XML (eXtensible Markup Language) file which contains all pertinent configuration information for running the web application. The SRI relies on the following portions of the deployment descriptor: servlet definitions; tag library references; and security constraints. The XML parsing rules for this file are contained in a DTD (Document Type Definition) which can be found at http://java.sun.com/j2ee/dtds/web-app_(—)2_(—)2.dtd. Refer to the JSP specification (above) for more information on deployment descriptors.

Servlet Definitions

The SRI incorporates a number of utility servlets (server-side Java applets which conform to the CGI specification). Servlets are identified in a <servlet> section within web.xml. A name is assigned to each servlet (which is used in creating a servlet mapping, described below), and this name is equated with the appropriate class-file name (specified relative to the Schemalive/WEB-INF/classes subdirectory). For example, a given servlet might be identified as follows:

<servlet> <servlet-name>DataDictionaryServlet</servlet-name> <servlet-class> dbUtils.DataDictionaryServlet </servlet-name> </servlet> By this definition, the following path should exist: Schemalive/WEB-INF/classes/dbUtils/DataDictionaryServlet.class

Note that the <servlet-name> does not represent the actual URL (Uniform Resource Locator) for the servlet; a separate mapping from <servlet-name> to URL occurs in a <servlet-mapping> section:

<servlet-mapping> <servlet-name>DataDictionaryServlet</servlet-name> <url-pattern>DataDictionaryServlet</servlet-name> </servlet-mapping>

By this definition (and assuming the root directory is Schemalive), the URL:

-   -   http://<host name>:<port>/Schemalive/DataDictionaryServlet

would cause the J2EE container to execute the code found in

-   -   Schemalive/WEB-INF/classes/dbUtils/DataDictionaryServlet.class

Tag Library References

A tag library contains Java code that implements custom HTML tags for use within JSPs. When the JSP engine encounters such tags, it makes corresponding Java calls into the tag libraries. For more information, refer to the JSP specification.

A <taglib> section within web.xml maps a URI (as used from within the JSP) to a tag library descriptor (which contains information about the associated class name, method calls, tag parameters). Below is a sample <taglib> section:

<taglib> <taglib-uri>view</taglib-uri> <taglib-location>WEB-INF/taglib/view.tld</taglib-location> </taglib>

See http://java.sun.com/j2ee/dtds/web-jsptaglib_(—)1_(—)1.dtd for the XML DTD for taglib.

The following is the contents of Schemalive/WEB-INF/taglib/view.tld:

<taglib> <tlibversion>1.0</tlibversion> <jspversion>1.2</jspversion> <tag> <name>setVars</name> <tagclass>tagUtils.ViewTag</tagclass> <teiclass>tagUtils.ViewTagExtraInfo</teiclass> <bodycontent>JSP</bodycontent> <attribute> <name>defaultEntryPoint</name> <required>true</required> <rtexprvalue>true</rtexprvalue> </attribute> <attribute> <name>dbName</name> <required>true</required> <rtexprvalue>true</rtexprvalue> </attribute> <attribute> <name>dbConn</name> <required>true</required> <rtexprvalue>true</rtexprvalue> </attribute> </tag> </taglib> The important parts are the <name>, <tagclass>, and <attribute> tags. The classes referenced in <taglclass> must lie along the J2EE-container's CLASSPATH (note that the Schema.live/WEB-INF/classes directory is automatically included in the CLASSPATH). Combined with <taglib-uri>, there is enough information now to use the custom tag within a JSP. One such invocation would look like this:

<view:setvars defaultEntryPoint=o“<%= entryPoints[O) %>” dbName=oll <%= dbName %>” dbConn“, II<%= dbConnName %>”> </view:setVars>

Notice the use of <taglib-uri>, <name>, and <attributes> within the custom tag. Also, it is perfectly legal to use JSP inline variables, such as <%=entryPoints[0]%>, as the example shows.

Security Constraints

web.xml contains information about how the SRI web application should handle security. This includes specifying what to secure, and how—as well as who can access the application (which is governed by the role names to which the user is assigned). The assignment of users to roles, however, is the responsibility of the J2EE container, and is handled differently by the different containers. The <security-constraint> section controls what is protected, and establishes the corresponding role. name, while the <login-config> section establishes the user-authentication method. Here is a sample:

<security-constraint> <web-resource-collection> <web-resource-name>Schemalive</web-resource-name> <url-pattern>/*</url-pattern> <http-method>GET</http-method> <http-method>POST</http-method> </web-resource-collection> <auth-constraint> <role-name>Schemalive</role-name> </auth-constraint> </security-constraint> <login-config> <auth-method>BASIC</auth-method> <realm-name>Schemalive</realm-name> </login-config>

Within the <web-resource-collection> section, the <url-pattern> tag protects the entire application (i.e., “/*”) for the GET and POST methods. The <auth-constraint> tag references a role named Schemalive; somewhere within the container's configuration, this role is defined and a set of userids and passwords associated with it. The 5 <login-con fig> section establishes BASIC as the authentication method; this is what will cause the userid/password prompt to pop-up when first accessing the site.

Connection Pooling

The SRI accomplishes database connectivity through the use of connection pooling, as defined in the JDBC 2.0 specification. (For documentation, see http://java.sun.com/j2se/1.3/docs/guide/jdbc/index.html.)

In connection pooling, a specified number of connections are pre-made to the underlying RDBMS (Oracle, in the reference implementation) at container start-up time. Connections are “borrowed”—that is, checked in and out of this pool—by program threads on an as-needed basis, without being opened, initialized, closed each time. This provides a dramatic improvement in the application's performance. The mechanics of the connection pool are largely hidden from the software; the standard API calls for opening and closing connections are used, although in actuality the corresponding connections are merely being checked in and out of the pool. The particular interfaces used for connection pooling can be found in the API documentation at http://java.sun.com/products/jdbc/jdbc20.stdext.javadoc/. (The pertinent classes are javax.sql.ConnectionPoolDataSource and javax.sql.PooledConnection.)

A static handle to the connection pool is managed through the dbUtils.SQLUtil class, which is implemented in

Schemalive/WEB-INF/classes/dbUtils/SQLUtil.java. This class obtains handles to pool connections using the Oracle JDBC 2.0 driver interface; the Javadocs for this API can be found at http://download.oracle.com.otn/utilities_drivers/jdbc/817/javadoc.tar.

A file named Schemalive/WEB-INF/classes/Connection.properties will need to be customized for each particular installation. JDBCURL contains a (properly formatted) string to reference the Oracle database-server instance. The SRI currently references the Type 2 JDBC driver, and the corresponding URL is in the formal jdbc.oracle:ocl8:@<tns name>. The user and pwd properties refer to the credentials the SRI will use for database access; if/when these values need to change, the server must be restarted in order for those changes to take effect.

Run-Time Maintenance

To enhance system performance (by reducing the need for real-time database qtleries), the SRI maintains two caches of information.

The first is called the DataDictionary, and contains all of the metadata derived by interrogating the schema (comprising table and column names, column datatypes and sizes, referential-integrity constraints, check constraints, and view definitions). The second is called BalloonHelp, and contains all of the help information specified in the base-tables HELP_OBJECT and HELP_SCHEMA.

When changes are made to the schema structure, or to the records in the help tables, these cached objects must (variously) be refreshed. This can be done dynamically, without having to restart the container.

The DataDictionary is rebuilt by referencing the JSP DataDictionary.jsp. There are three options when rebuilding the DataDictionary: Only, Views (with check), and Views (without check). The “Only” option simply rebuilds the DataDictionary object (i.e., re-interrogates the database) without rebuilding any (system-generated) views. The other two modes regenerate these views on the fly; the “with check” mode checks to see if a given view (for a corresponding table) already exists, and rebuilds the view only if it is not found. The “without check” option does a brute-force rebuild of all system-generated views, regardless of whether or not they are already defined.

Note that while the DataDictionary is being rebuilt (which can be a lengthy process, depending on the size of the schema), users will be blocked from accessing the application.

BalloonHelp is rebuilt by referencing the JSP BalloonHelp.jsp. The current contents of the BalloonHelp object are displayed along with a link to rebuild. When the link is clicked, the cached object is refreshed from the base-tables.

Changes that are stored to these cached objects are immediately reflected within the application.

Because of its adherence to various open-standard specifications, the SRI is not dependent on anyone container, but rather, can operate in any J2EE compliant container. The only customization that should be required to run the SRI in a particular environment are the variables (mentioned above and) defined within the Schemalive/WEB-INF/classes/dbUtils/SQLUtil.java file.

It is evident that the embodiment described above accomplishes the stated objects of the invention. While the presently preferred embodiment has been described in detail, it will be apparent to those skilled in the art that the principles of the invention are realizable by other implementations, structures, and configurations without departing from the scope and spirit of the invention, as defined in the appended claims. 

The invention claimed is:
 1. A method for managing state within an end-user interface for working with the data within a relational database, the end-user interface operating under control of a processor, the relational database comprising a plurality of tables, constraints and relationships and also operating under control of a processor, said method comprising providing a hierarchical context stack for suspending the working state of a primary table within the relational database while drilling-down across a relationship to work with related information in a subordinate table within the relational database, wherein the relational database may be any arbitrary relational database, and said method is effective regardless of the size or complexity of the database, wherein said method is applied recursively, so that the working state of the subordinate table is suspended while drilling-down across a further relationship to work with related information in a further-subordinated table, wherein said method further comprises imposing (as necessary) within the hierarchical context stack a constraining working context on the further-subordinated table, so as to reveal and enforce any relational interdependency between the subordinate and further-subordinated tables. 